home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Windows Expert
/
Windows Expert.iso
/
windownt
/
perlnt.zip
/
ANNOUNCE
next >
Wrap
Text File
|
1993-07-25
|
3KB
|
76 lines
Newsgroups: comp.os.ms-windows.programmer.win32
From: clark@clark.b11.ingr.com (Clark Williams)
Subject: Perl for NT (part 0 of 3)
Sender: usenet@b30news.b30.ingr.com (Usenet Feed)
Organization: Intergraph Corporation
Date: Wed, 26 May 1993 15:17:18 GMT
Lines: 68
What follows in this and the next three articles, is my port of Perl
4.036 to Microsoft's Windows NT operating system. This port has been
in use at Intergraph for little over a month and has experienced no
major crashes. Supplied with the source patches is the test suite that
we've been using to prevent regressions. It is a modified version of
the stock perl test suite, using a different driver (testnt.cmd) and a
different test file extension (.nt instead of .t).
DISCLAIMER
This code is supplied on an as-is basis, with no warranty or support
implied. You are welcome to modify and redistribute this code to your
hearts content, as long as credit is given where credit's due.
END DISCLAIMER
Ok, now that that's over with, on to the good stuff.
INSTALLATION
Check out the file README for instructions on installing this stuff.
PROBLEMS
There are some features of the perl language that are missing from
this port of perl. Mainly it's because NT doesn't support various
features. Either that or because I didn't have time to port them. A
short list of missing features is:
- fork, fcntl, ioctl, syscall, chroot
- pipe, wait, umask, socketpair
- process group/parent process access
- access to password/group/*ent files
- symlinks
- setuid/setgid
- various fields in stat structure
For a complete list of what's implemented, what's not, and what may
come in the future, look at the files README, relnotes.txt and
status.txt. There is a perl script in the eg directory called
status.txt that summarizes the current status of the port by parsing
the file. Useless but cute.
A feature that is in this release is access to the NT registry
database via predefined user subroutines. See the file registry.txt
and usersubs.txt for more info. The registry access API's are
documented in the Win32 API Reference help file, under System Services
and Registry and Initialization Files.
Hopefully this will be of use to someone. I've been using it regularly
since it first compiled. I actually used the perl debugger to assist
in debugging perl. Run perl running the perl debugger under WinDbg.
Step the perl script till it gets ready to fail and then set a
breakpoint using WinDbg to look at the guts of perl. Weird.
If anyone finds a bug (quick look at the sky to see if lightning is
about to get me), please mail me a test case. I can't promise a quick
response, but I'll try to fix it. It depends on how much time my slave
driver of a boss gives me to work on perl. Just kidding about the
slave driver thing, Mary. No, really, it's a joke.
--
"If we don't go anywhere with this | Clark Williams
then we aren't going to get | Software Development Tools
anywhere" | Intergraph Corporation
C. Williams (Yogi Berra clone) | clark@clark.b11.ingr.com